Stopwatch and timer user interfaces

ABSTRACT

An electronic device may display a first lap time representation, and may move the first lap time representation in accordance with a first amount of elapsed time. While moving the first lap time representation, the electronic device may detect a lap input. In response to the lap input, the electronic device may cease movement of the first lap time representation, display a second lap time representation, and move the second lap time representation in accordance with a second amount of elapsed time. A relative positioning of the first lap time representation and the second lap time representation may correspond to a difference between a first lap time and a second lap time. In some embodiments, the electronic device may update the timescales of lap time representation(s) in accordance with a rotational input. In some embodiments, the electronic device may update a timer duration setting in accordance with a rotational input.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/044,979, entitled “STOPWATCH AND TIMER USER INTERFACES,” filedSep. 2, 2014, and U.S. Provisional Patent Application No. 62/129,825,entitled “STOPWATCH AND TIMER USER INTERFACES,” filed Mar. 7, 2015,which are hereby incorporated by reference in their entirety.

This application relates to: U.S. Provisional Patent Applicationentitled “Context-Specific User Interfaces,” filed Sep. 2, 2014, namingChristopher Wilson as the inventor, International Patent ApplicationSerial No. PCT/US2013/040061, entitled “Device, Method, and GraphicalUser Interface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, and International Patent ApplicationSerial No. PCT/US2013/069483, entitled “Device, Method, and GraphicalUser Interface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013. The contents of the aboveapplications are hereby incorporated by reference in their entirety forall purposes.

BACKGROUND

1. Field

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for representing lap times,adjusting timescales and setting timers in the context of a stopwatch ora timer.

2. Description of Related Art

Modern electronic devices may provide various timing functionalities.For example, electronic devices may provide stopwatch functionalitiesand/or timer functionalities. However, some of these functionalities maybe limited in that they may display timing data in a basic manner, maynot allow for user customization of timing data display parameters,and/or may not provide intuitive methods for inputting timing values bya user. There is a need for more efficient, user-friendly procedures fordisplaying timing data, allowing for user customization of timing datadisplay parameters, and inputting timing values.

BRIEF SUMMARY

In some embodiments, a method of representing lap times in a userinterface of an electronic device comprises: displaying, at a firsttime, a first representation of a first lap time in a user interface;moving the first representation along a first axis in the user interfacein accordance with a first amount of time elapsed since the first time,the first amount of time corresponding to the first lap time; whilemoving the first representation, detecting a first lap input at thedevice at a second time; in response to the first lap input: ceasingmovement of the first representation along the first axis; anddisplaying a second representation of a second lap time in the userinterface; and moving the second representation along the first axis inthe user interface in accordance with a second amount of time elapsedsince the second time, the second amount of time corresponding to thesecond lap time, wherein a relative positioning of the firstrepresentation and the second representation along the first axiscorresponds to a difference between the first lap time and the secondlap time.

In some embodiments, a method of updating the timescale of a lap timerepresentation in a user interface of an electronic device comprises:displaying a first representation of a current lap time, the firstrepresentation having a first timescale and including a first element,the first element positioned with respect to the first timescale inaccordance with the current lap time on the first timescale; whiledisplaying the first representation, detecting a rotational movement ofa rotatable input mechanism; and in response to the rotational movement:updating the first representation of the current lap time to have asecond timescale, different from the first timescale, in accordance withthe rotational movement; and updating the position of the first elementin accordance with the current lap time on the second timescale.

In some embodiments, a method of updating a current duration setting ofa timer in a user interface of an electronic device comprises:displaying a timer representation in a user interface, the timerrepresentation including: an analog representation, the analogrepresentation including a current duration indicator representing acurrent duration setting, and a digital representation representing thecurrent duration setting; while displaying the timer representation,detecting a rotational movement of the rotatable input mechanism; and inresponse to the rotational movement, updating the current durationindicator and the digital representation in accordance with therotational movement.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having atouch-sensitive display in accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display and a rotatable input mechanism inaccordance with some embodiments.

FIG. 5B illustrates a portable multifunction device having atouch-sensitive display and a rotatable input mechanism in accordancewith some embodiments.

FIGS. 6A-6Q illustrate exemplary user interface(s) for representing laptime(s) in the user interface(s) of electronic device(s).

FIGS. 7A-7D illustrate exemplary user interface(s) for updating thetimescale(s) of lap time representation(s) in the user interface(s) ofelectronic device(s).

FIGS. 8A-8K illustrate exemplary user interface(s) for updating currentduration setting(s) of timer(s) in the user interface(s) of electronicdevice(s).

FIGS. 9A-9B are a flow diagram illustrating a process for representinglap times in a user interface of an electronic device.

FIG. 10 is a flow diagram illustrating a process for updating thetimescale of a lap time representation in a user interface of anelectronic device.

FIG. 11 is a flow diagram illustrating a process for updating a currentduration setting of a timer in a user interface of an electronic device.

FIG. 12 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 13 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 14 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 15 is a functional block diagram of an electronic device inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

It is desirable for a device to provide efficient, user-friendlyprocedures for displaying timing data (e.g., displaying lap times andtheir representations), allowing for user customization of timing datadisplay parameters (e.g., allowing for user modification of timescalesof timing elements), and inputting timing values (e.g., allowing forrobust entry of timer settings). Below, FIGS. 1A-1B, 2, 3, 4A-4B, and5A-5B provide a description of exemplary devices that optionally performlap time representing, timescale adjusting and timer setting techniques.FIGS. 6-8 illustrate exemplary user interfaces involved in the abovetechniques. The user interfaces in the figures are also used toillustrate the lap time representing, timescale adjusting and timersetting processes described below, including the processes in FIGS.9-11.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience, and is sometimesknown as or called a touch-sensitive display system. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on the touchsensitive surface, or to a substitute (proxy) for the force or pressureof a contact on the touch sensitive surface. The intensity of a contacthas a range of values that includes at least four distinct values andmore typically includes hundreds of distinct values (e.g., at least256). Intensity of a contact is, optionally, determined (or measured)using various approaches and various sensors or combinations of sensors.For example, one or more force sensors underneath or adjacent to thetouch-sensitive surface are, optionally, used to measure force atvarious points on the touch-sensitive surface. In some implementations,force measurements from multiple force sensors are combined (e.g., aweighted average) to determine an estimated force of a contact.Similarly, a pressure-sensitive tip of a stylus is, optionally, used todetermine a pressure of the stylus on the touch-sensitive surface.Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure and the estimated force or pressure isused to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/or applicationspecific integrated circuits.

Memory 102 may include one or more computer readable storage mediums.The computer readable storage mediums may be tangible andnon-transitory. Memory 102 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 122 may control access tomemory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips. RF (radio frequency) circuitry 108receives and sends RF signals, also called electromagnetic signals. RFcircuitry 108 converts electrical signals to/from electromagneticsignals and communicates with communications networks and othercommunications devices via the electromagnetic signals. RF circuitry 108optionally includes well-known circuitry for performing these functions,including but not limited to an antenna system, an RF transceiver, oneor more amplifiers, a tuner, one or more oscillators, a digital signalprocessor, a CODEC chipset, a subscriber identity module (SIM) card,memory, and so forth. RF circuitry 108 optionally communicates withnetworks, such as the Internet, also referred to as the World Wide Web(WWW), an intranet and/or a wireless network, such as a cellulartelephone network, a wireless local area network (LAN) and/or ametropolitan area network (MAN), and other devices by wirelesscommunication. The RF circuitry 108 optionally includes well-knowncircuitry for detecting near field communication (NFC) fields, such asby a short-range communication radio. The wireless communicationoptionally uses any of a plurality of communications standards,protocols and technologies, including but not limited to Global Systemfor Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE),high-speed downlink packet access (HSDPA), high-speed uplink packetaccess (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-CellHSPA (DC-HSPDA), long term evolution (LTE), near field communication(NFC), wideband code division multiple access (W-CDMA), code divisionmultiple access (CDMA), time division multiple access (TDMA), Bluetooth,Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 801.11n and/or IEEE 802.11ac),voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail(e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161 and one or more input controllers 160 forother input or control devices. The one or more input controllers 160receive/send electrical signals from/to other input or control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, infrared port, USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 and convertthe detected contact into interaction with user-interface objects (e.g.,one or more soft keys, icons, web-pages or images) that are displayed ontouch screen 112. In an exemplary embodiment, a point of contact betweentouch screen 112 and the user corresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereas touchsensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device, so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112 which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112 which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and other touchsensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementationsa user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast or other visual property) of graphicsthat are displayed. As used herein, the term “graphics” includes anyobject that can be displayed to a user, including without limitationtext, web pages, icons (such as user-interface objects including softkeys), digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video Conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 may be used to manage an address book orcontact list (e.g., stored in application internal state 192 of contactsmodule 137 in memory 102 or memory 370), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 137, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contacts module137, and telephone module138, video conference module 139 includes executable instructions toinitiate, conduct, and terminate a video conference between a user andone or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web-pages or portionsthereof, as well as attachments and other files linked to web-pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web-page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 112 or on an external, connected display via external port124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions; data on stores and otherpoints of interest at or near a particular location; and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 152, FIG. 1A). In some embodiments, memory 102may store a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177 or GUI updater 178 to update the application internalstate 192. Alternatively, one or more of the application views 191include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of the aboveidentified modules corresponds to a set of instructions for performing afunction described above. The above identified modules or programs(e.g., sets of instructions) need not be implemented as separatesoftware programs, procedures or modules, and thus various subsets ofthese modules may be combined or otherwise rearranged in variousembodiments. In some embodiments, memory 370 may store a subset of themodules and data structures identified above. Furthermore, memory 370may store additional modules and data structures not described above.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online Video”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 are labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments the touch sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface) may haveone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data thatrepresents the intensity of touches. The user interface of device 500can respond to touches based on their intensity, meaning that touches ofdifferent intensities can invoke different user interface operations ondevice 500.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013 and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 may be a rotatable input device or a depressible androtatable input device, for example. Input mechanism 508 may be abutton, in some examples.

Input mechanism 508 may be a microphone, in some examples. Personalelectronic device 500 can include various sensors, such as GPS sensor532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, and/or a combination thereof, all ofwhich can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 900-1100 (FIGS. 9A, 9B,10, and 11). The computer-executable instructions can also be storedand/or transported within any non-transitory computer readable storagemedium for use by or in connection with an instruction execution system,apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. For purposes of this document, a“non-transitory computer readable storage medium” can be any medium thatcan tangibly contain or store computer-executable instructions for useby or in connection with the instruction execution system, apparatus, ordevice. The non-transitory computer readable storage medium can include,but is not limited to, magnetic, optical, and/or semiconductor storages.Examples of such storage include magnetic disks, optical discs based onCD, DVD, or Blu-ray technologies, as well as persistent solid-statememory such as flash, solid-state drives, and the like. Personalelectronic device 500 is not limited to the components and configurationof FIG. 5B, but can include other or additional components in multipleconfigurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of device 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example,an image (e.g., icon), a button, and text (e.g., hyperlink) may eachconstitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In, some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of: an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms eliminatenarrow spikes or dips in the intensities of the swipe contact forpurposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments the contact-detection intensity threshold is zero.In some embodiments the contact-detection intensity threshold is greaterthan zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the term “open application” or “executing application”refers to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application may be any one of thefollowing types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes) which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed to towards user interfaces (“UI”) andassociated processes that may be implemented on a multifunction devicewith a display and a touch-sensitive surface, such as devices 100, 300,and/or 500 (FIGS. 1A, 3A, and/or 5A), to provide lap time representing,timescale adjusting and timer setting functionalities.

1. Representing Lap Times

Multifunction devices, such as devices 100, 300, and/or 500 (FIGS. 1A,3A, and/or 5A), may provide various stopwatch functionalities. Some suchfunctionalities optionally include tracking the amount of time elapsedsince a specified moment in time (e.g., since selection of a “start”button), tracking one or more lap times, and any other functionalitythat may be associated with a stopwatch. The embodiments described beloware directed to multifunction device(s) that provide such stopwatchfunctionalities.

FIG. 6A illustrates exemplary electronic device 600 and exemplaryassociated user interface. Electronic device 600 may be any one ofdevices 100, 300, and/or 500 (FIGS. 1A, 3A, and/or 5A). In theillustrated embodiment, device 600 is a wearable device. In someembodiments, device 600 provides one or more stopwatch functionalities,one of which may be representing lap times. Device 600 optionallydisplays one or more user interfaces for representing the lap times.

The user interface displayed by device 600 in FIG. 6A optionallyincludes a digital stopwatch representation 602. Digital stopwatchrepresentation 602 optionally includes a minutes portion (far-leftportion), a seconds portion (middle portion), and a 1/10^(th) secondportion (far-right portion), though it is understood that digitalstopwatch representation 602 may have any appropriate structure. Digitalstopwatch representation 602 optionally displays the total time elapsedafter “start” button 604 is selected. In some embodiments, the userinterface includes button 606, which can be inactive until button 604has been selected, as will be described in more detail below.

In the illustrated embodiment, button 604 has been selected by finger608. It is understood that while the embodiments in this disclosure maybe described as involving finger interaction (e.g., selection of a userinterface button with a finger), the scope of the disclosure is not solimited. Any appropriate interaction with the user interfaces of thedisclosure is within the scope of the disclosure, including interactionwith objects such as a stylus. Further, it is understood that userinterface input elements (e.g., buttons) may be replaced by physicalinput elements while remaining within the scope of the disclosure.

FIG. 6B illustrates an exemplary user interface presented by device 600in response to detecting selection of button 604 to start timing withdigital stopwatch representation 602. Button 604 optionally changes froma “start” button to a “stop” button, selection of which optionally stopstiming with digital stopwatch representation 602. Additionally, button606 optionally becomes active as a “lap” button, selection of whichoptionally delineates and defines one lap time from another lap time,the details of which will be further described below.

Lap time representation 610 is optionally displayed in the userinterface in response to selection of button 604 in FIG. 6A. Lap timerepresentation 610 optionally represents a lap (in this case, the firstlap after selection of button 604 in FIG. 6A, as indicated by lap numberrepresentation 612). Though lap time representation 610 is illustratedas a dot, it is understood that any suitable user interface element maybe used to represent laps in accordance with the embodiments of thedisclosure (e.g., squares, triangles, etc.). As time elapses, lap timerepresentation 610 optionally moves along a specified axis in the userinterface. For example, lap time representation 610 optionally movesvertically in the user interface as time elapses; it is understood,however, that lap time representation 610 may move in any otherdirection along any other axis in the user interface within the scope ofthe disclosure.

FIG. 6C illustrates an exemplary user interface presented by device 600after 25 seconds have elapsed since selection of button 604 in FIG. 6A.Digital stopwatch representation 602 reflects the total elapsed time of25 seconds.

Lap time representation 610 optionally moves vertically in the userinterface in accordance with the amount of time that has elapsed sinceselection of button 604 in FIG. 6A (i.e., in accordance with 25seconds). Although lap time representation 610 is illustrated as havingmoved directly from its initial location to its current location, it isunderstood that lap time representation 610 optionally moves in acontinuous manner in the user interface in accordance with the passageof time. For example, at a point in time when 12.5 seconds had elapsedsince selection of button 604 in FIG. 6A, lap time representation 610was optionally located at a point in the middle of its initial location(in FIG. 6B) and its current location (in FIG. 6C).

FIG. 6D illustrates an exemplary user interface presented by device 600after 35 seconds have elapsed since selection of button 604 in FIG. 6A.Digital stopwatch representation 602 reflects the total elapsed time of35 seconds. Lap time representation 610 has optionally further movedvertically in the user interface in accordance with the additional 10seconds that have elapsed since FIG. 6C. Additionally, “lap” button 606has been selected to define the end of the first lap.

FIG. 6E illustrates an exemplary user interface presented by device 600after selection of button 606 in FIG. 6D. In response to the selectionof button 606 in FIG. 6D, lap time representation 610 optionally stopsmoving vertically in the user interface, because the end of the lapassociated with lap time representation 610 (i.e., the first lap) hasoptionally been defined by the selection of button 606 in FIG. 6D.Additionally, lap time representation 614, which optionally correspondsto the second lap as indicated by lap number representation 616, isoptionally displayed in the user interface. Lap time representation 614is optionally displayed at the same initial vertical position in theuser interface as the initial vertical position of lap timerepresentation 610 in FIG. 6B.

To allow for the display of lap time representation 614 and lap numberrepresentation 616 in the user interface, lap time representation 610and lap number representation 612 are optionally moved horizontally tothe left (i.e., in a direction orthogonal to the vertical axis) in theuser interface in response to the selection of button 606 in FIG. 6D. Insome embodiments, the horizontal movement of lap time representation 610and lap number representation 612 is optionally animated. Additionally,lap time representation 610 and lap time representation 614 areoptionally connected by line 618. It is understood that in someembodiments, lap time representations (e.g., lap time representation610) are initially displayed on the left side of the user interface, andadditional lap time representations are added to the right of them—insuch embodiments, existing lap time representations optionally do notneed to be moved horizontally when a new lap time representation isadded to the user interface (except when the horizontal space in theuser interface becomes completely filled with lap time representations,in which case older lap time representations are optionally shifted offthe user interface, but can be scrolled back into view in response toany appropriate input for doing so).

FIG. 6F illustrates an exemplary user interface presented by device 600after 20 seconds have elapsed since selection of button 606 in FIG. 6E(and after 55 seconds have elapsed since selection of button 604 in FIG.6A). Digital stopwatch representation 602 reflects the total elapsedtime of 55 seconds since selection of button 604 in FIG. 6A. Asdiscussed before, lap time representation 610 is optionally located atthe same vertical position as in FIG. 6E, because the lap time for thelap associated with lap time representation 610 (i.e., the first lap)has optionally already been defined and set.

Lap time representation 614 optionally moves vertically in the userinterface in accordance with the passage of 20 seconds since selectionof button 606 in FIG. 6E. Lap time representation 614 optionally movesin a manner similar to as described previously with respect to lap timerepresentation 610. Line 618 optionally continues to connect lap timerepresentation 610 and lap time representation 614.

FIG. 6G illustrates an exemplary user interface presented by device 600after 25 seconds have elapsed since selection of button 606 in FIG. 6E(and after 60 seconds have elapsed since selection of button 604 in FIG.6A). Digital stopwatch representation 602 reflects the total elapsedtime of 60 seconds (i.e., one minute) since selection of button 604 inFIG. 6A. Lap time representation 614 has optionally moved furthervertically in the user interface in accordance with the additional fiveseconds that have elapsed since FIG. 6F. Additionally, “lap” button 606has been selected by finger 608.

FIG. 6H illustrates an exemplary user interface presented by device 600after selection of button 606 in FIG. 6G. Similar to as described beforewith respect to FIG. 6E, in response to selection of button 606 in FIG.6G, lap time representation 614 optionally stops moving vertically inthe user interface, because the end of the lap associated with lap timerepresentation 614 (i.e., the second lap) has optionally been defined byselection of button 606 in FIG. 6G. Additionally, lap timerepresentation 620, which optionally corresponds to the third lap asindicated by its corresponding lap number representation, is optionallydisplayed in the user interface. Lap time representation 620 isoptionally displayed at the same initial vertical position in the userinterface as the initial vertical position of lap time representation610 in FIG. 6B and lap time representation 614 in FIG. 6E. Additionally,lap time representation 614 and lap time representation 620 areoptionally connected by a line.

As before, in order to allow for the display of lap time representation620 and its corresponding lap number representation in the userinterface, lap time representation 610 and its corresponding lap numberrepresentation, and lap time representation 614 and its correspondinglap number representation, are optionally moved horizontally to the leftin the user interface in response to the selection of button 606 in FIG.6G.

Because full lap times have been defined for the first lap and thesecond lap, an average lap time is optionally determined and displayedin the user interface. The average lap time is optionally the averagelap time of all fully-defined laps since selection of “start” button 604in FIG. 6A. The average lap time is optionally indicated by average laptime indicator 622 in the user interface, which is optionally ahorizontal line at a vertical position corresponding to the time valueof the average lap time (in this case, 30 seconds). Average lap timeindicator 622 is optionally a dashed line, as illustrated. In theillustrated embodiment, average lap time indicator 622 is positionedbetween lap time representation 610 and lap time representation 614,because the average lap time of 30 seconds is optionally between 35seconds (the lap time associated with lap time representation 610) and25 seconds (the lap time associated with lap time representation 614).

FIG. 6I illustrates an exemplary user interface presented by device 600when lap time representation 620 has reached a maximum time on timescale626 in the user interface. Digital stopwatch representation 602 reflectsthe total elapsed time of 110 seconds (i.e., one minute and fiftyseconds) since selection of button 604 in FIG. 6A. The user interfaceoptionally has timescale 626 that can display a minimum and a maximumlap time. For example, timescale 626 can optionally display a minimumlap time of 0 seconds and a maximum lap time of 50 seconds. Timescale626 is optionally the same timescale that was in FIGS. 6A-6H, though itwas not illustrated for ease of description. In the embodiment of FIG.61, lap time representation 620 has moved (e.g., continuously moved)from its initial position to a position corresponding to 50 seconds—themaximum lap time that can be displayed by timescale 626.

In some embodiments, timescale 626 optionally continuously changes astime continues to elapse, and as lap time representation 620 continuesto correspond to a lap time that is longer than 50 seconds. In someembodiments, timescale 626 optionally does not change until the lapassociated with lap time representation 620 has been fully-defined(e.g., by selection of the “lap” button), as will be described below.

FIG. 6J illustrates an exemplary user interface presented by device 600when lap time representation 620 has exceeded a maximum lap time ontimescale 626 in the user interface. In the embodiment illustrated inFIG. 6J, timescale 626 optionally does not change until the lapassociated with lap time representation 620 has been fully-defined(e.g., by selection of the “lap” button), as mentioned above. Thus,despite 20 seconds having elapsed since the time illustrated in FIG. 6I(as indicated by the total elapsed time of 130 seconds (i.e., twominutes and ten seconds) in digital stopwatch representation 602), laptime representation 620 has exhibited no further vertical movement inthe user interface, because lap time representation 620 has optionallyalready exceeded the maximum lap time that can be displayed on timescale626. As illustrated, “lap” button 606 has been selected by finger 608.

FIG. 6K illustrates an exemplary user interface presented by device 600after selection of button 606 in FIG. 6J. Similar to as describedbefore, the lap time representations and their corresponding lap numberrepresentations have moved horizontally to the left in the userinterface to allow for display of lap time representation 624 and itcorresponding lap number representation. Additionally, the average laptime has been re-determined to be 43.3 seconds based on fully-definedlap times of 35 seconds (for the first lap), 25 seconds (for the secondlap), and 70 seconds (for the third lap). The average lap time of 43.3seconds is reflected by average lap time indicator 622.

Additionally, timescale 626 has been adjusted to allow for display ofall of the fully-defined lap times. For example, timescale 626 isoptionally adjusted to have a maximum lap time that is greater than anyof the fully-defined lap times. In the illustrated embodiment, timescale626 has been adjusted to display a minimum lap time of 0 seconds and amaximum lap time of 90 seconds. The vertical positions of the lap timerepresentations and average lap time indicator 622 are optionally alsoadjusted in accordance with the adjusted timescale 626 so as to beappropriately positioned in the user interface with respect to theadjusted timescale 626.

At any point in FIGS. 6B-6K, a user may wish to view a list of lap timesin addition to the lap time representations discussed above. In someembodiments, a list of lap times is optionally displayed in response todetection of a specified input at device 600 (e.g., a specified input onthe touch-sensitive surface of device 600). FIG. 6L illustrates anexemplary input detected at device 600 for displaying a list of laptimes associated with the lap time representations displayed in the userinterface. In the embodiment illustrated, a vertical swipe by finger 608has been detected on the touch-sensitive surface of device 600. Thevertical swipe may be detected at any location on the touch-sensitivesurface of device 600.

FIG. 6M illustrates an exemplary user interface presented by device 600after detection of the vertical swipe in FIG. 6L. In response to thevertical swipe detected by device 600 in FIG. 6L, a display area of thelap time representations is optionally reduced so as to allow display oflap time list 628 in the user interface. These smaller lap timerepresentations are illustrated as reduced-size lap time representations630. In some embodiments, the reduction in the display area of the laptime representations is performed as vertical swipe is being detected onthe touch-sensitive surface of device 600. As stated above, the userinterface also includes lap time list 628. The lap times in lap timelist 628 optionally correspond to the lap times represented by the laptime representations discussed previously, as well as reduced-size laptime representations 630. Lap time list 628 optionally includes the lapnumber for each lap, and the lap time for each lap. Lap time list 628may be scrolled vertically up and down in response to vertical swipegestures detected on the touch-sensitive surface of device 600. The userinterface illustrated in FIG. 6M thus allows a user to view lap times aslap time representations (reduced-size lap time representations 630) andas a list (lap time list 628).

Device 600 is optionally able to display various stopwatch views.Further, a user is optionally able to switch between the variousstopwatch views in response to specified inputs at device 600 for doingso (e.g., from a menu bar including a list of stopwatch views from whichto choose, in response to a specified gesture detected at device 600, inresponse to detection of a specified mechanical input at device, etc.).In some examples, a menu or selection of stopwatch views are optionallydisplayed in response to an input including a contact detected on atouch-sensitive surface of device 600 (sometimes, anywhere on thetouch-sensitive surface of the device), the contact having acharacteristic intensity greater than an intensity threshold. Whenswitching between the various stopwatch views, stopwatch data isoptionally preserved. That is to say that data relating to the number oflaps recorded so far, the lap times associated with each, the averagelap time, the length of the current lap, the total elapsed time of alllaps, and any other data relating to the laps discussed above isoptionally preserved on device 600 when switching between the stopwatchviews. As a result, the different stopwatch views are able to accessand/or present that preserved data in, perhaps, a different manner.

The embodiments described with reference to FIGS. 6A-6M are optionallyassociated with a first stopwatch view (e.g., a graph stopwatch view).FIG. 6N illustrates an exemplary user interface presented by device 600for displaying lap times in a second stopwatch view (e.g., an analogstopwatch view). A user may have switched to the analog stopwatch viewfrom the graph stopwatch view, but this need not be the case (e.g., theuser may have started timing in the analog stopwatch view). The userinterface in the analog stopwatch view of FIG. 6N optionally includesanalog dial 632, which has a timescale of 0-60 seconds and has hand 634to indicate a current lap time on the timescale of 0-60 seconds. Analogdial 632 is optionally used to track seconds that have elapsed in acurrent lap. Analog dial 638 optionally has a timescale of 0-30 minutes,and is optionally used to track minutes that have elapsed in a currentlap. Lap times over 60 seconds in length are optionally tracked using acombination of analog dial 638 and analog dial 632. For example, todisplay a lap time of one minute thirty seconds, analog dial 638optionally displays one minute of time, and analog dial 632 optionallydisplays 30 seconds of time. It is understood that the timescales of0-60 seconds for analog dial 632 and 0-30 minutes for analog dial 638are exemplary only, and do not limit the scope of the disclosure.

The user interface in FIG. 6N also optionally includes digital stopwatchrepresentation 636 for displaying the current lap time in a digitalmanner Digital stopwatch representation 636 optionally includes aminutes portion (far-left portion), a seconds portion (middle portion),and a 1/10^(th) second portion (far-right portion), though it isunderstood that different structures for digital stopwatchrepresentation 636 are possible. Selection of “lap” button 606optionally delineates and defines laps similar to as describedpreviously with reference to FIGS. 6A-6M.

As before, a user may wish to view a list of lap times in addition tothe analog lap time representation discussed above. In some embodiments,a list of lap times is optionally displayed in response to detection ofa specified input at device 600 (e.g., a specified input on thetouch-sensitive surface of device 600). FIG. 6O illustrates an exemplaryinput detected at device 600 for displaying a list of lap times thathave been delineated and defined by selection of “lap” button 606. Asbefore, in the embodiment illustrated, a vertical swipe by finger 608has been detected on the touch-sensitive surface of device 600. Thevertical swipe may be detected at any location on the touch-sensitivesurface of device 600.

FIG. 6P illustrates an exemplary user interface presented by device 600after detection of the vertical swipe in FIG. 6O. In response to thevertical swipe detected by device 600 in FIG. 60, display areas ofanalog dials 632 and/or 638 are optionally reduced so as to allowdisplay of lap time list 628. The reduced-sized analog dials 632 and 638are optionally displayed in an upper region 642 of the user interface.Analog dials 632 and 638 optionally retain the same timescales they hadin FIGS. 6N-6O. An additional analog dial 640 is optionally added to theuser interface in region 642. Analog dial 640 optionally has a timescaleof 0-1 second in units of 1/10^(th) of a second. Analog dial 640 isoptionally used to track tenths of a second that have elapsed in acurrent lap. In some embodiments, the reduction in the display area ofanalog dials 632 and/or 638, and the addition of analog dial 640, isperformed as vertical swipe is being detected on the touch-sensitivesurface of device 600. It is understood that the timescale of 0-1 secondfor analog dial 640 is exemplary only, and does not limit the scope ofthe disclosure.

The user interface also optionally includes lap time list 628. Lap timelist 628 optionally includes the lap number for each lap, and the laptime for each lap. Lap time list 628 may be scrolled vertically up anddown in response to vertical swipe gestures detected on thetouch-sensitive surface of device 600. The user interface illustrated inFIG. 6P thus allows a user to view the current lap time as an analog laptime representation (in region 642), and allows the user to view a listof lap times (lap time list 628).

As stated above, the embodiments described with reference to FIGS. 6A-6Mare optionally associated with a first stopwatch view (e.g., a graphstopwatch view), and the embodiments described with reference to FIGS.6N-6P are optionally associated with a second stopwatch view (e.g., ananalog stopwatch view). FIG. 6Q illustrates an exemplary user interfacepresented by device 600 for displaying lap times in a third stopwatchview (e.g., a hybrid stopwatch view). The hybrid stopwatch view caninclude aspects of the graph stopwatch view and the analog stopwatchview. Reduced-size lap time representations 630 can display theheretofore recorded lap times, including the current lap time, asdiscussed above with respect to FIGS. 6A-6M. Analog dials 644 candisplay the current lap time as discussed above with respect to FIGS.6N-6P. Finally, digital stopwatch representation 636 can display thecurrent lap time in a digital manner.

In some embodiments, the units of digital stopwatch representation 636align spatially with the units of analog dials 644. That is, theleft-most dial of analog dials 644 optionally displays minutes, as doesthe left-most portion of digital stopwatch representation 636; themiddle dial of analog dials 644 optionally displays seconds, as does themiddle portion of digital stopwatch representation 636; and theright-most dial of analog dials 644 optionally displays 1/10^(th) of asecond, as does the right-most portion of digital stopwatchrepresentation 636.

It is noted that although FIGS. 6A-6Q illustrate various user interfacesof device 600, the described techniques may be extended to cover otherdevices, such as devices 100, 300, and/or 500 (FIGS. 1A, 3A, and 5A).That is to say, various electronic devices may display the userinterfaces described in FIGS. 6A-6Q. For brevity, those details are notexplicitly discussed here. Further, it is understood that the order ofuser interfaces and operations described with reference to FIGS. 6A-6Qis exemplary only, and does not limit the scope of the disclosure. Forexample, the vertical swipe in FIG. 6L could have instead been inputtedat FIG. 6F to similarly display a list of lap times.

2. Adjusting Timescales

Multifunction devices, such as devices 100, 300, and/or 500 (FIGS. 1A,3A, and/or 5A), may provide various timing or stopwatch functionalities.As part of these functionalities, these devices may display timingelements having certain timescales. A user may adjust the timescales ofthe timing elements in various ways. The embodiments described below aredirected to multifunction device(s) in which the timescales of timingelements may be adjusted by a user.

FIG. 7A illustrates exemplary electronic device 700 and exemplaryassociated user interface. Electronic device 700 may be any one ofdevices 100, 300, and/or 500 (FIGS. 1A, 3A, and/or 5A). In theillustrated embodiment, device 700 is a wearable device. In someembodiments, device 700 provides one or more stopwatch functionalities,one of which may be adjusting the timescales of stopwatchrepresentations (e.g., adjusting the timescale of an analog stopwatchrepresentation, adjusting the timescale of a digital stopwatchrepresentation, etc.). Device 700 optionally displays one or more userinterfaces for adjusting such timescales.

The user interface displayed by device 700 in FIG. 7A optionallyincludes analog stopwatch representation 702 for representing a currentlap time. Analog stopwatch representation 702 optionally has a specifiedtimescale—in this case, 0-60 seconds—and optionally includes hand 704,which is optionally positioned with respect to the specified timescalein accordance with the current lap time. In the illustrated embodiment,hand 704 is positioned on the timescale at a position corresponding tofive seconds—the elapsed time of the current lap.

Analog stopwatch representation 702 optionally also includes analogstopwatch representation 706. Analog stopwatch representation706optionally has a timescale different than analog stopwatchrepresentation 702 for representing the current lap time. For example,analog stopwatch representation optionally has a timescale of 0-30minutes (not illustrated for ease of description). The timescalesprovided for analog stopwatch representations 702 and 706 are exemplaryonly, and do not limit the scope of the disclosure.

A user may wish to adjust the timescales of analog stopwatchrepresentation 702 and/or analog stopwatch representation 706. Adjustingof the above timescales may be accomplished in response to detection ofa specified input at device 700. For example, a rotational input ofrotatable input mechanism 701 on device 700 optionally allows foradjusting of the timescales of analog stopwatch representation 702and/or analog stopwatch representation 706. In the embodimentillustrated in FIG. 7A, finger 708 is providing a rotational input torotatable input mechanism 701.

FIG. 7B illustrates an exemplary user interface presented by device 700while the rotational input is detected at rotatable input mechanism 701in FIG. 7A. Finger 708 can continue to provide rotational input atrotatable input mechanism 701 in FIG. 7B. The amount of rotational inputdetected at rotatable input mechanism 701 so far optionally correspondsto an amount of input for changing the timescale of analog stopwatchrepresentation 702 from 0-60 seconds (in FIG. 7A) to 0-45 seconds (inFIG. 7B). In response to the rotational input detected so far, thetimescale of analog stopwatch representation 702 optionally changes inaccordance with the rotational input as the rotational input isdetected. For example, the timescale displayed in FIG. 7A optionally“stretches” (e.g., shifts in a circular manner) as the rotational inputis detected at rotatable input mechanism 701, by an amount defined by acorrespondence of an amount of rotational input to an amount oftimescale change. For example, half a rotation of rotatable inputmechanism 701 may correspond to increasing or decreasing a timescale by50%.

In conjunction with the change in the timescale of analog stopwatchrepresentation 702, the position of hand 704 with respect to the updatedtimescale is optionally updated so as to maintain the correspondence ofthe position of hand 704 to the current lap time (in this case, fiveseconds).

In some embodiments, the timescale of analog stopwatch representation706 is optionally similarly updated in response to detection of therotational input at rotatable input mechanism 701. In some embodiments,the timescale of analog stopwatch representation 706 is optionallyconcurrently updated with the updating of the timescale of analogstopwatch representation 702 (not illustrated for ease of description).For example, in the illustrated embodiment, the timescale of analogstopwatch representation 706 may be changed from 0-30 minutes (in FIG.7A) to 0-22.5 minutes (in FIG. 7B) in accordance with the amount ofrotational input detected at rotatable input mechanism 701.

FIG. 7C illustrates an exemplary user interface presented by device 700after cessation of the rotational input detected at rotatable inputmechanism 701 in FIG. 7B. In some embodiments, after cessation of therotational input at rotatable input mechanism 701, the timescales ofanalog stopwatch representations 702 and/or 706 remain as they last werewhen the rotational input was last detected. For example, in theembodiment illustrated, the rotational input was terminated when thetimescale of analog stopwatch representation 702 had been changed to0-45 seconds. Thus, in some embodiments, the timescale of analogstopwatch representation 702 remains at 0-45 seconds after cessation ofthe rotational input detected at rotatable input mechanism 701. Thetimescale of analog stopwatch representation 706 optionally similarlyremains after cessation of the rotational input detected at rotatableinput mechanism 701 (not illustrated for ease of description).

FIG. 7D illustrates an alternative exemplary user interface presented bydevice 700 after cessation of the rotational input detected at rotatableinput mechanism 701 in FIG. 7B. In some embodiments, after cessation ofthe rotational input at rotatable input mechanism 701, the timescales ofanalog stopwatch representations 702 and/or 706 “snap” to the closestpredefined timescale of a plurality of predefined timescales thatcorrespond to the direction of the rotational input (e.g., whether therotational input is increasing or decreasing the timescales of analogstopwatch representations 702 and/or 706).

For example, analog stopwatch representation 702 is optionallyassociated with four predefined timescales: 0-60 seconds, 0-30 seconds,0-6 seconds and 0-3 seconds; similarly, analog stopwatch representation706 is optionally associated with four predefined timescales: 0-30minutes, 0-15 minutes, 0-3 minutes and 0-2 minutes. When the rotationalinput is terminated at rotatable input mechanism 701, the timescale ofanalog stopwatch representation 702 optionally “snaps” to 0-30 secondsinstead of remaining at 0-45 seconds (as illustrated in FIG. 7D),because 0-45 seconds is optionally not one of the four predefinedtimescales that analog stopwatch representation 702 is associated with,and because 0-30 seconds optionally corresponds to the direction of therotational input (decreasing of the timescale of analog stopwatchrepresentation 702). The position of hand 704 is optionally also updatedin correspondence with the “snapping” of the timescale of analogstopwatch representation 702. Though not illustrated, it is understoodthat the timescale of analog stopwatch representation 706 optionallyalso “snaps” to a predefined timescale. It is understood that theprovided predefined timescales are exemplary only, and do not limit thescope of the disclosure.

It is noted that although FIGS. 7A-7D illustrate various user interfacesof device 700, the described techniques may be extended to cover otherdevices, such as devices 100, 300, and/or 500 (FIGS. 1A, 3A, and 5A).That is to say, various electronic devices may display the userinterfaces described in FIGS. 7A-7D. For brevity, those details are notexplicitly discussed here.

3. Setting Timer Duration

Multifunction devices, such as devices 100, 300, and/or 500 (FIGS. 1A,3A, and/or 5A), may provide various timing functionalities. As part ofthese functionalities, these devices may provide for a countdown timerto countdown from a specified current duration setting. A user mayadjust the current duration setting in various ways. The embodimentsdescribed below are directed to multifunction device(s) in which thecurrent duration setting of a timer may be adjusted by a user.

FIG. 8A illustrates exemplary electronic device 800 and an exemplaryassociated user interface. Electronic device 800 may be any one ofdevices 100, 300, and/or 500 (FIGS. 1A, 3A, and/or 5A). In theillustrated embodiment, device 800 is a wearable device. In someembodiments, device 800 provides one or more timer functionalities, oneof which may be setting a timer duration. Device 800 optionally displaysone or more user interfaces for setting the timer duration.

The user interface displayed by device 800 in FIG. 8A optionallyincludes a timer representation having analog representation 802 anddigital representation 806. Analog representation 802 optionally has aspecified timescale (in this case, 0-12 hours), and includes currentduration indicator 804 for representing a current duration setting (inthis case, five hours and 30 minutes) on the specified timescale. Insome embodiments, current duration indicator 804 represents the value ofa specified unit of the current duration setting that corresponds to theunit of the timescale of analog representation 802 (in this case,hours). In some embodiments, current duration indicator 804 representsthe entire current duration setting; in such embodiments, currentduration indicator 804 would optionally be positioned between the 5 andthe 6 on the timescale of analog representation 802 to represent thecurrent duration setting of five hours and 30 minutes.

Digital representation 806 optionally includes an hours portion forrepresenting the hours unit of the current duration setting (in thiscase, five hours), and a minutes portion for representing the minutesunit of the current duration setting (in this case, 30 minutes). It isunderstood that other structures for digital representation 806 arepossible. Analog representation 802 and digital representation 806optionally represent the current duration setting in a coordinatedmanner (e.g., if the current duration setting is changed, digitalrepresentation 806 and analog representation 802 are optionally bothupdated to reflect the change).

The user interface in FIG. 8A also optionally includes button 807 tostart counting down from the current duration setting, and button 809for resetting the countdown to the initial current duration settingvalue.

A user may wish to adjust the current duration setting of analogrepresentation 802 and/or digital representation 806. Adjusting of thecurrent duration setting may be accomplished in response to detection ofa specified input at device 800. For example, a rotational input ofrotatable input mechanism 801 on device 800 optionally allows foradjusting of the current duration setting.

FIG. 8B illustrates an exemplary user interface presented by device 800while a rotational input is detected at rotatable input mechanism 801.Finger 808 is optionally providing a rotational input to rotatable inputmechanism 801. In response to the rotational input, the current durationsetting is optionally changed in accordance with the rotational input.In the illustrated embodiment, the rotational input has reduced thecurrent duration setting from five hours and 30 minutes to four hoursand 30 minutes. The updated current duration setting is optionallyreflected by digital representation 806. The updated current durationsetting is optionally also reflected by the changed position of currentduration indicator 804 on analog representation 802. As illustrated,current duration indicator 804 has moved from being positioned at the 5to being positioned at the 4 on the timescale of analog representation802 in accordance with the rotational input. In some embodiments,current duration indicator 804 is moved as the rotational input isdetected.

In some embodiments, analog representation 802 and/or digitalrepresentation 806 can be presented in 12-hour format (e.g., asillustrated in FIG. 8A) or 24-hour format (not illustrated). Whiledevice 800 is displaying user interface analog representation 802 and/ordigital representation 806, the device can detect a touch input on itstouch-sensitive surface. In accordance with a touch input that has acharacteristic intensity greater than a predetermined thresholdintensity, device 800 presents one or more affordances for selectingbetween 12- and 24-hour display formats. The affordance(s) optionallyindicate the currently selected display format by highlighting thecurrent format selection. In some embodiments, analog representation802—when in 24-hour format—displays twenty-four marked increments alongthe circumference of analog representation 802 (instead of twelve asshown in FIG. 8A). In some embodiments, analog representation 802 in24-hour format displays twelve, two-hour increments (e.g., clock facemarkers are labeled 0, 2, 4, and so forth). In accordance with a touchinput that has a characteristic intensity lower that the predeterminedthreshold intensity, device 800 provides user interface responses suchas those described below with reference to FIG. 8C-8G.

In some embodiments, before supplying the rotational input at rotatableinput mechanism 801, a user optionally specifies which unit of thecurrent duration setting is to be changed by the rotational input. FIG.8C illustrates a user's designation of the hours unit of the currentduration setting to be changed by subsequent rotational inputs detectedat rotatable input mechanism 801. As stated before, digitalrepresentation 806 optionally has hours portion 810 and minutes portion811. One of the two portions of digital representation may be selectedor designated to specify which unit of the current duration setting(e.g., hours or minutes) will be changed by subsequent rotational inputsdetected at rotatable input mechanism 801. For example, hours portion810 may be selected (as illustrated) to specify that the hours unit ofthe current duration setting will be changed by subsequent rotationalinput detected at rotatable input mechanism 801. Alternatively, minutesportion 811 may be selected to specify that the minutes unit of thecurrent duration setting will be changed by subsequent rotational inputdetected at rotatable input mechanism 801. As illustrated, finger 808has selected hours portion 810 of digital representation 806.

FIG. 8D illustrates an exemplary user interface presented by device 800after selection of hours portion 810 in FIG. 8C. In response to theselection of hours portion 810, a visual cue is optionally displayed inthe user interface to signify that hours portion 810 has been selected.For example, hours portion 810 is optionally highlighted, beginsflashing, or is displayed within a border (or any other visual cue isprovided for signifying the selection of hours portion 810). In theillustrated embodiment, a box 812 is displayed around hours portion 810to signify its selection.

Additionally, the timescale of analog representation 802 is optionallyupdated in response to the selection of hours portion 810 to be atimescale associated with hours portion 810. For example, the timescaleof analog representation 802 is optionally updated to be 0-12 hours inresponse to selection of hours portion 810. Other timescales mayalternatively be associated with hours portion 810 instead of the 0-12hour timescale. If the timescale of analog representation 802 is already0-12 hours, the timescale need not be updated in response to theselection of hours portion 810 (as is the case in FIG. 8D).

FIG. 8E illustrates an exemplary user interface presented by device 800in response to detection of rotational input at rotatable inputmechanism 801. Finger 808 has provided a rotational input at rotatableinput mechanism 801. Because hours portion 810 is selected, rotationalinput at rotatable input mechanism 801 optionally changes the hours unitof the current duration setting. Digital representation 806 optionallyreflects this change (in this case, change from four to two hours).Additionally, current duration indicator 804 is optionally updated toreflect the change in the hours unit of the current duration setting, asillustrated.

FIG. 8F illustrates a user's designation of the minutes unit of thecurrent duration setting to be changed by subsequent rotational inputsdetected at rotatable input mechanism 801. Hours portion 810 may becurrently selected, as discussed previously. As illustrated, finger 808has selected minutes portion 811 of digital representation 806 todesignate that the minutes unit of the current duration setting will bechanged by subsequent rotational inputs detected at rotatable inputmechanism 801.

FIG. 8G illustrates an exemplary user interface presented by device 800after selection of minutes portion 811 in FIG. 8F. In response to theselection of minutes portion 811, a visual cue is optionally displayedin the user interface to signify that minutes portion 811 has beenselected. For example, minutes portion 811 is optionally highlighted,begins flashing, or is displayed within a border (or any other visualcue is provided for signifying the selection of minutes portion 811). Inthe illustrated embodiment, a box 812 is displayed around minutesportion 811 to signify its selection.

Additionally, the timescale of analog representation 802 is optionallyupdated in response to the selection of minutes portion 811 to be atimescale associated with minutes portion 811. For example, thetimescale of analog representation 802 is optionally updated to be 0-60minutes in response to selection of minutes portion 811, as illustrated.Other timescales may alternatively be associated with minutes portion811 instead of the 0-60 minute timescale. If the timescale of analogrepresentation 802 is already 0-60 minutes, the timescale need not beupdated to reflect the selection of minutes portion 811.

FIG. 8H illustrates an exemplary user interface presented by device 800in response to detection of rotational input at rotatable inputmechanism 801. Finger 808 has provided a rotational input at rotatableinput mechanism 801. Because minutes portion 811 is selected, rotationalinput at rotatable input mechanism 801 optionally changes the minutesunit of the current duration setting. Digital representation 806optionally reflects this change (in this case, change from 30 to 40minutes). Additionally, current duration indicator 804 is optionallyupdated to reflect the change in the minutes unit of the currentduration setting, as illustrated.

FIG. 8I illustrates a user's starting of a timer countdown from thecurrent duration setting. As discussed previously, selection of button807 optionally starts a timer countdown from the current durationsetting. As illustrated, finger 808 has selection “start” button 807.

FIG. 8J illustrates an exemplary user interface presented by device 800after selection of “start” button 807 in FIG. 8I. Button 807 optionallychanges from a “start” button in FIG. 81 to a “stop” button in FIG. 8Jfor stopping the timer countdown initiated in FIG. 8I. Additionally,digital representation 806 is optionally updated to reflect the timeelapsed since selection of “start” button 807 in FIG. 8I. In theillustrated embodiment, five seconds have elapsed since selection of“start” button 807 in FIG. 8I. Additionally, current duration indicator804 is optionally also updated to reflect the time elapsed, asillustrated by its change from its position next to 40 in the timescaleof analog representation 802 to its position next to 35 in the timescaleof analog representation 802.

FIG. 8K illustrates an alternative form for current duration indicator804. In some embodiments, instead of being a dot (as illustrated inFIGS. 8A-8J), current duration indicator 804 is optionally a regionhaving a filled area that extends from a position on the timescale ofanalog representation 802 that corresponds to 0, to a position on thetimescale of analog representation 802 that corresponds to the value ofthe currently-selected unit of the current duration setting (in thiscase, 35 minutes). In all other respects, current duration indicator 804of FIG. 8K optionally behaves in a manner similar to current durationindicator 804 of FIGS. 8A-8J. For example, current duration indicator804 optionally expands or contracts around the perimeter of analogrepresentation 802 as the minutes (or hours) unit of the currentduration setting is changed, whether due to a rotational input detectedat rotatable input mechanism 801 or a timer countdown.

It is noted that although FIGS. 8A-8K illustrate various user interfacesof device 800, the described techniques may be extended to cover otherdevices, such as devices 100, 300, and/or 500 (FIGS. 1A, 3A, and 5A).That is to say, various electronic devices may display the userinterfaces described in FIGS. 8A-8K. For brevity, those details are notexplicitly discussed here. Further, it is understood that the order ofuser interfaces and operations described with reference to FIGS. 8A-8Kis exemplary only, and does not limit the scope of the disclosure. Forexample, a user may have selected and changed the minutes portion ofdigital timer representation 806 before selecting and changing the hoursportion of digital timer representation 806.

FIGS. 9A-9B are a flow diagram illustrating process 900 for representinglap times in a user interface of an electronic device. Process 900 maybe carried out by electronic devices such as devices 100, 300, and/or500 (FIGS. 1A, 3A, 5A) in various embodiments. At block 902, theelectronic device displays (e.g., on a touch-sensitive display), at afirst time, a first representation (e.g., a first dot) of a first laptime in a user interface.

At block 904, the electronic device moves the first representation alonga first axis (e.g., a vertical axis) in the user interface in accordancewith a first amount of time elapsed since the first time, the firstamount of time corresponding to the first lap time (e.g., moves thefirst representation in a continuous manner along the first axis as timecontinues to elapse after the first time). At block 906, while movingthe first representation, the electronic device detects a first lapinput at the device (e.g., detects selection of a lap button in the userinterface on the touch-sensitive display) at a second time.

At block 908, in response to the first lap input, the electronic device:ceases movement of the first representation along the first axis, anddisplays a second representation (e.g., a second dot) of a second laptime in the user interface at block 910. For example, in response to thefirst lap input, the electronic device freezes the first representationat the location in the user interface at which the first representationwas located when the first lap input was detected, and adds the secondrepresentation to the user interface.

At block 912, the electronic device moves the second representationalong the first axis (e.g., a vertical axis) in the user interface inaccordance with a second amount of time elapsed since the second time,the second amount of time corresponding to the second lap time (e.g.,moves the second representation in a continuous manner along the firstaxis as time continues to elapse after the second time). In someembodiments, a relative positioning of the first representation and thesecond representation along the first axis corresponds to a differencebetween the first lap time and the second lap time. For example, in someembodiments, the second representation will be shown below the firstrepresentation while the second lap time is less than the first laptime, and will move in the direction of the first axis as the second laptime gets closer to the first lap time; as the second lap time exceedsthe first lap time, the second representation will be shown above thefirst representation, and will continue to move in the direction of thefirst axis as the second lap time increasingly exceeds the first laptime.

In some embodiments, the first and second representations are separatedby a distance (e.g., a constant distance) in a direction orthogonal tothe first axis (e.g., horizontally separated) in the user interface. Insome embodiments, the first and second representations are connected bya line in the user interface.

In some embodiments, the first and second representations comprise afirst stopwatch view. The electronic device optionally detects a viewchange input at the device (e.g., an input on a touch-sensitive displayto switch to a different stopwatch view). In response to the view changeinput, the electronic device optionally displays a second stopwatch view(e.g., an analog stopwatch view, a digital stopwatch view, etc.),different from the first stopwatch view, the second stopwatch viewincluding information about the first lap time and the second lap time.For example, information about the first lap time, corresponding to thefirst representation, and the second lap time, corresponding to thesecond representation, is optionally preserved when switching from thefirst stopwatch view to the second stopwatch view. The second stopwatchview optionally displays this information in a manner different from thefirst and second representations of the first stopwatch view. Forexample, the second stopwatch view is optionally a digital stopwatchview that displays the first and second lap times as part of a list oflap times.

In some embodiments, the electronic device detects a lap time displayinput on a touch-sensitive surface of the device (e.g., on atouch-sensitive display of the device), the lap time display inputcomprising a contact and movement of the contact (e.g., a verticalflick) on the touch-sensitive surface. In response to the lap timedisplay input, the electronic device optionally displays a list of laptimes including the first lap time and the second lap time. In someembodiments, in response to the lap time display input, the electronicdevice modifies the display of the first and second representations soas to reduce a display area of the first and second representations inthe user interface (e.g., reducing the display area of the first andsecond representations, and displaying the list of lap times at leastpartially in the area in the user interface made available as a resultof reducing the display area of the first and second representations).

In some embodiments, a first dimension of the user interface along thefirst axis is displayed at a first timescale, the first timescale havinga first maximum lap time (e.g., the vertical dimension of the userinterface, and the corresponding timescale, are such that a maximum laptime of “the first maximum lap time” can be displayed. For example, thevertical dimension and the corresponding timescale can be such that amaximum lap time of one minute can be displayed), and the second laptime exceeds the first maximum lap time (e.g., the second lap time islonger than one minute). While the second lap time exceeds the firstmaximum lap time, the electronic device optionally detects a second lapinput at the device (e.g., detecting selection of a lap button in theuser interface on a touch-sensitive display) at a third time. Inresponse to the second lap input, the electronic device optionallydetermines a second timescale having a second maximum lap time greaterthan the second lap time (e.g., determining a timescale greater than thesecond lap time so that the second lap time can be displayed on thetimescale), and updates the first dimension of the user interface tohave the second timescale. For example, updating the first dimensionoptionally includes updating the location of the first representation inthe user interface to maintain the proper relative positioning of thefirst representation with respect to the second timescale. Additionally,if the timescale is increased, the rate of movement of the first,second, and further representations is optionally decreased to maintainthe proper correspondence between movement and elapsed time. In someembodiments, the timescale of the first dimension is updated afterdetecting the second lap input, and the second representation remainsstationary at the maximum point of the first dimension until thetimescale is updated.

In some embodiments, the first representation and the secondrepresentation provide respective visual cues of their respective laptimes. For example, the representation corresponding to the longest lapoptionally provides a first visual cue, the representation correspondingto the shortest lap optionally provides a second visual cue. Forexample, the representation corresponding to the longest lap time isoptionally a red dot, and the representation corresponding to theshortest lap time is optionally a green dot. The representationcorresponding to the current lap optionally flashes between green andwhite while its corresponding lap time is shorter than the shortest lap,turns to solid white while its corresponding lap time is longer than theshortest lap but shorter than the longest lap, and solid red while itscorresponding lap time is longer than the longest lap. If therepresentation corresponding to the current lap becomes the longest lap,the previous longest lap, which was optionally solid red, optionallyturns solid white when the current lap representation turns solid red.Other colors and/or visual cues can similarly be utilized in this manner

In some embodiments, the electronic device displays a stopwatchrepresentation (e.g., a digital stopwatch, and/or an analog stopwatch)in addition to the first representation and the second representation,the stopwatch representation including information about the second laptime. For example, the stopwatch representation optionally displays thesecond lap time at the same time and in addition to the first and secondrepresentations. However, the stopwatch representation optionallydisplays the second lap time in a format different from the firstrepresentation and the second representation. For example, the first andsecond representations may present lap time information in the form of aline graph, while the stopwatch representation may present lap timeinformation—in particular the second lap time information—in the form ofa digital stopwatch representation.

In some embodiments, the electronic device detects a second lap input atthe device (e.g., detecting selection of a lap button in the userinterface on a touch-sensitive display) at a third time, the third timebeing after the second time. In response to the second lap input, theelectronic device optionally determines an average lap time based on thefirst lap time and the second lap time (e.g., determining an average laptime of some or all of the lap times recorded as representations alongthe first axis), and displays a representation of the average lap timein the user interface. For example, the electronic device optionallydisplays a line orthogonal to the first axis at a point on the firstaxis that corresponds to the average lap time. In this way, the relativepositioning of the first/second representations and the average lap timeline optionally indicates the relative lengths of the first/second laptimes with respect to the average lap time.

In some embodiments, the electronic device, prior to moving the firstrepresentation along the first axis (e.g., a vertical axis) in the userinterface, measures the first amount of time elapsed since the firsttime, wherein moving the first representation along the first axis is inaccordance with the measured first amount of time, and, prior to movingthe second representation along the first axis (e.g., a vertical axis)in the user interface, measures the second amount of time elapsed sincethe second time, wherein moving the second representation along thefirst axis is in accordance with the measured second amount of time.

FIG. 10 is a flow diagram illustrating process 1000 for updating thetimescale of a lap time representation in a user interface of anelectronic device. Process 1000 may be carried out by electronic devicessuch as devices 100, 300, and/or 500 (FIGS. 1A, 3A, 5A) in variousembodiments. At block 1002, the electronic device, which includes arotatable input mechanism, displays (e.g., on a touch-sensitive display)a first representation (e.g., an analog dial) of a current lap time in auser interface. The first representation has a first timescale (e.g.,0-60 seconds, 0-30 seconds, 0-6 seconds, 0-3 seconds) and includes afirst element (e.g., an analog watch/timer hand), the first elementpositioned with respect to the first timescale in accordance with thecurrent lap time on the first timescale. For example, the analog handmay be positioned at 25 seconds on a 30 second timescale in accordancewith a current lap time being 25 seconds, or may be positioned at 5seconds on the 30 second timescale in accordance with the current laptime being 35 seconds.

At block 1004, while displaying the first representation, the electronicdevice detects a rotational movement of the rotatable input mechanism Atblock 1006, in response to the rotational movement, the electronicdevice updates the first representation of the current lap time to havea second timescale, different from the first timescale, in accordancewith the rotational movement. For example, the electronic deviceincreases or decreases the timescale based on the rotational directionof the rotational input. At block 1006, the electronic device alsoupdates the position of the first element in accordance with the currentlap time on the second timescale. For example, if the analog hand waspositioned to point at a location corresponding to 25 seconds on a 30second timescale, when the timescale is changed to 60 seconds, theposition of the analog hand will be changed to point to a new locationcorresponding to 25 seconds on the 60 second timescale.

In some embodiments, updating the first representation to have thesecond timescale comprises selecting the second timescale from aplurality of predefined timescales (e.g., predefined timescales of 60seconds, 30 seconds, 6 seconds and 3 seconds). In some embodiments, therotational movement of the rotatable input mechanism corresponds to afirst input timescale, different from each of the plurality ofpredefined timescales (e.g., the rotational movement of the rotatableinput mechanism optionally corresponds to changing the timescale from 60seconds to 20 seconds), and selecting the second timescale from theplurality of predefined timescales comprises determining which of theplurality of predefined timescales is closest to the first inputtimescale, and selecting the closest timescale of the predefinedtimescales as the second timescale. For example, if the rotationalmovement of the rotatable input mechanism optionally corresponds tochanging the timescale from 60 seconds to 20 seconds, selecting 30seconds as the second timescale as opposed to 6 seconds, because 30seconds is closer to 20 seconds than is 6 seconds.

In some embodiments, updating the first representation comprisesdisplaying an animation of the first representation changing from thefirst timescale to the second timescale (e.g., shrinking or stretchingthe first representation's timescale from the current timescale to thenew timescale). In some embodiments, the first representation of thecurrent lap time (e.g., main dial) includes a second representation ofthe current lap time (e.g., sub-dial), the second representation havinga third timescale, different from the first timescale. In response tothe rotational movement, the electronic device optionally updates thesecond representation of the current lap time to have a fourthtimescale, different from the second timescale, in accordance with therotational movement (e.g., increasing or decreasing the timescale of asub-dial based on the rotational movement of the rotational input and incoordination with changes in the timescale of the main dial. Forexample, updating a 30 minute sub-dial of a 60 second main dial to be a15 minute sub-dial of a 30 second main dial).

FIG. 11 is a flow diagram illustrating process 1100 for updating acurrent duration setting of a timer in a user interface of an electronicdevice. Process 1100 may be carried out by electronic devices such asdevices 100, 300, and/or 500 (FIGS. 1A, 3A, 5A) in various embodiments.At block 1102, the electronic device, which includes a rotatable inputmechanism, displays (e.g., on a touch-sensitive display) a timerrepresentation in a user interface. The timer representation includes,at block 1104, an analog representation (e.g., an analog dial), theanalog representation including a current duration indicator (e.g., adot, a line, a filled region) representing a current duration setting(e.g., a current timer countdown setting). The timer representation alsoincludes a digital representation (e.g., hours and minutes) representingthe current duration setting.

At block 1106, while displaying the timer representation, the electronicdevice detects a rotational movement of the rotatable input mechanism Atblock 1108, in response to the rotational movement, the electronicdevice updates the current duration indicator and the digitalrepresentation in accordance with the rotational movement. For example,the electronic device updates the current duration indicator in theanalog representation and the digital representation in a coordinatedmanner to reflect the current duration setting as the current durationsetting is changed in response to the rotational input.

In some embodiments, prior to detecting the rotational movement of therotatable input mechanism, the electronic device detects selection ofthe first portion of the digital representation (e.g., a user optionallyselects/touches the hours indicator of the digital representation on atouch-sensitive display), wherein updating the current durationindicator and the digital representation comprises: updating a firstunit (e.g., the hours unit) of the current duration setting inaccordance with the rotational movement and the selection of the firstportion of the digital representation (e.g., because the first portionof the digital representation is selected, the rotational movementoptionally changes a first unit (e.g., hours) of the current durationsetting, and not a second unit (e.g., minutes) of the current durationsetting); and updating the current duration indicator and the firstportion of the digital representation to reflect the updated first unit(e.g., hours) of the current duration setting.

In some embodiments, in response to detecting the selection of the firstportion of the digital representation, the electronic device displays afirst visual cue indicating the selection of the first portion of thedigital representation (e.g., highlighting the first portion of thedigital representation, displaying a box or outline around the firstportion of the digital representation, causing the first portion of thedigital representation to flash, etc.).

In some embodiments, the digital representation comprises a firstportion (e.g., an hours indicator) and a second portion (e.g., a minutesindicator). The electronic device optionally detects selection of thesecond portion of the digital representation (e.g., a user optionallyselects/touches the minutes indicator of the digital representation on atouch-sensitive display). The electronic device optionally detects asecond rotational movement of the rotatable input mechanism. In responseto the second rotational movement, the electronic device optionallyupdates a second unit (e.g., minutes) of the current duration setting,different from the first unit, in accordance with the second rotationalmovement and the selection of the second portion of the digitalrepresentation (e.g., because the second portion of the digitalrepresentation is selected, the rotational movement optionally changesthe second unit (e.g., minutes) of the current duration setting, and notthe first unit (e.g., hours) of the current duration setting), andupdates the current duration indicator and the second portion of thedigital representation to reflect the updated second unit (e.g.,minutes) of the current duration setting. In some embodiments, inresponse to detecting the selection of the second portion of the digitalrepresentation, the electronic device displays a second visual cueindicating the selection of the second portion of the digitalrepresentation (e.g., highlighting the second portion of the digitalrepresentation, displaying a box or outline around the second portion ofthe digital representation, causing the second portion of the digitalrepresentation to flash, etc.).

In some embodiments, in response to detecting the selection of the firstportion (e.g., the hours portion) of the digital representation, theelectronic device updates the analog representation to have a firstpredefined timescale corresponding to the first unit (e.g., hours) ofthe current duration setting (e.g., when the hours portion of thedigital representation is selected, the analog representation isoptionally updated to have a timescale of 0-12 hours). In someembodiments, in response to detecting the selection of the secondportion (e.g., the minutes portion) of the digital representation, theelectronic device updates the analog representation to have a secondpredefined timescale corresponding to the second unit (e.g., minutes) ofthe current duration setting (e.g., when the minutes portion of thedigital representation is selected, the analog representation isoptionally updated to have a timescale of 0-60 minutes).

In some embodiments, the current duration indicator is located on aperimeter of the analog representation (e.g., the current durationindicator is optionally a dot or line or other indicator that is locatedaround the outside of a circular analog representation), and updatingthe current duration indicator comprises updating the location of thecurrent duration indicator along the perimeter of the analogrepresentation (e.g., moving the current duration indicator around theoutside of the circular analog in accordance with the rotationalmovement of the rotatable input mechanism). In some embodiments, thecurrent duration indicator comprises a dot. In some embodiments, thecurrent duration indicator comprises a region extending from a firstlocation along a perimeter of the analog representation (e.g., an analogdial location corresponding to 0 hours and/or 0 minutes) to a secondlocation along the perimeter of the analog representation (e.g., ananalog dial location corresponding to the hours and/or minutes of thecurrent duration setting), the first location corresponding to aduration setting of zero, and the second location corresponding to thecurrent duration setting. For example, the current duration indicator isoptionally a filled region that follows the perimeter/curve of an analogdial, and whose length is determined based on the length of the currentduration setting and the units displayed on the analog dial. Forexample, if the analog dial has a timescale of 0-12 hours, and the hoursunit of the current duration setting is 4 hours, the current durationindicator is optionally a filled region extending from 0 hours to 4hours around the perimeter of the analog dial.

FIG. 12 shows exemplary functional blocks of an electronic device 1200that, in some embodiments, performs the above-described features. Asshown in FIG. 12, an electronic device 1200 may include display unit1202 configured to display graphical objects; human input interface unit1204 configured to receive user input; and processing unit 1206 coupledto display unit 1202, and human input interface unit 1204.

In some embodiments, the processing unit 1206 includes a displayenabling unit 1210 and a measuring unit 1212. In some embodiments, thedisplay enabling unit 1210 is configured to cause a display of a userinterface (or portions of a user interface) in conjunction with thedisplay unit 1202. For example, the display enabling unit 1210 may beused for: displaying, at a first time, a first representation of a firstlap time in a user interface; displaying a first representation of acurrent lap time, the first representation having a first timescale andincluding a first element, the first element positioned with respect tothe first timescale in accordance with the current lap time on the firsttimescale; updating the first representation of the current lap time tohave a second timescale, different from the first timescale, inaccordance with a rotational movement of a rotatable input mechanism;and, displaying a timer representation in a user interface.

In some embodiments, the determining unit 1208 is configured todetermine various quantities. For example, determining unit 1208 maydetermine an average lap time based on a first lap time and a second laptime. Determining unit 1208 may also determine a timescale having amaximum lap time greater than a specified lap time. Determining unit1208 may determine which of a plurality of predefined timescales isclosest to an input timescale. In some embodiments, the measuring unit1212 is configured to measure various quantities. For example, measuringunit 1212 may measure an amount of time that has elapsed since aspecified time.

The units of FIG. 12 may be used to implement the various techniques andmethods described above with respect to FIGS. 6-11. The units of device1200 are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 12 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

In accordance with some embodiments, FIG. 13 shows a functional blockdiagram of an electronic device 1300 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 13 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 13, an electronic device 1300 includes a display unit1302 configured to display a graphic user interface, optionally, a touchsensitive surface unit 1304 configured to receive contacts, and aprocessing unit 1306 coupled to the display unit 1302 and, optionally,the touch-sensitive surface unit 1304. In some embodiments, theprocessing unit 1306 includes a display enabling unit 1308, a movingunit 1310, a detecting unit 1312, a ceasing unit 1314, a modificationenabling unit 1316, a determining unit 1318, an updating unit 1320, anda measuring unit 1322.

The processing unit 1306 is configured to enable display (e.g., with thedisplay enabling unit 1308), at a first time, a first representation ofa first lap time in a user interface; move (e.g., with the moving unit1310) the first representation along a first axis in the user interfacein accordance with a first amount of time elapsed since the first time,the first amount of time corresponding to the first lap time; whilemoving the first representation, detect (e.g., with the detecting unit1312) a first lap input at the device at a second time; in response tothe first lap input: cease (e.g., with the ceasing unit 1314) movementof the first representation along the first axis; and enable display(e.g., with the display enabling unit 1308) of a second representationof a second lap time in the user interface; and move (e.g., with themoving unit 1310) the second representation along the first axis in theuser interface in accordance with a second amount of time elapsed sincethe second time, the second amount of time corresponding to the secondlap time, wherein a relative positioning of the first representation andthe second representation along the first axis corresponds to adifference between the first lap time and the second lap time.

In some embodiments, the first and second representations are separatedby a distance in a direction orthogonal to the first axis in the userinterface.

In some embodiments, the first and second representations are connectedby a line in the user interface.

In some embodiments, the first and second representations comprise afirst stopwatch view, the processing unit further configured to: detect(e.g., with the detecting unit 1312) a view change input at the device;and in response to the view change input, enable display (e.g., with thedisplay enabling unit 1308) of a second stopwatch view, different fromthe first stopwatch view, the second stopwatch view includinginformation about the first lap time and the second lap time.

In some embodiments, the processing unit is further configured to:detect (e.g., with the detecting unit 1312) a lap time display input onthe touch-sensitive surface unit 1304, the lap time display inputcomprising a contact and movement of the contact on the touch-sensitivesurface unit 1304; and in response to the lap time display input, enabledisplay (e.g., with the display enabling unit 1308) of a list of laptimes including the first lap time and the second lap time.

In some embodiments, the processing unit is further configured to: inresponse to the lap time display input, enable modification (e.g., withthe modification enabling unit 1316) of the first and secondrepresentations so as to reduce a display area of the first and secondrepresentations in the user interface.

In some embodiments, a first dimension of the user interface along thefirst axis is displayed at a first timescale, the first timescale havinga first maximum lap time, and the second lap time exceeds the firstmaximum lap time, the processing unit further configured to: while thesecond lap time exceeds the first maximum lap time, detect (e.g., withthe detecting unit 1312) a second lap input at the device at a thirdtime; and in response to the second lap input: determine (e.g., with thedetermining unit 1318) a second timescale having a second maximum laptime greater than the second lap time; and update (e.g., with theupdating unit 1320) the first dimension of the user interface to havethe second timescale.

In some embodiments, the first representation and the secondrepresentation provide respective visual cues of their respective laptimes.

In some embodiments, the processing unit is further configured to:enable display (e.g., with the display enabling unit 1308) of astopwatch representation in addition to the first representation and thesecond representation, the stopwatch representation includinginformation about the second lap time.

In some embodiments, the processing unit is further configured to:detect (e.g., with the detecting unit 1312) a second lap input at thedevice at a third time, the third time being after the second time; inresponse to the second lap input, determine (e.g., with the determiningunit 1318) an average lap time based on the first lap time and thesecond lap time; and enable display (e.g., with the display enablingunit 1308) of a representation of the average lap time in the userinterface.

In some embodiments, the processing unit is further configured to: priorto moving the first representation along the first axis in the userinterface, measure (e.g., with the measuring unit 1322) the first amountof time elapsed since the first time, wherein moving the firstrepresentation along the first axis is in accordance with the measuredfirst amount of time; and prior to moving the second representationalong the first axis in the user interface, measure (e.g., with themeasuring unit 1322) the second amount of time elapsed since the secondtime, wherein moving the second representation along the first axis isin accordance with the measured second amount of time.

The operations described above with reference to FIG. 9A-9B are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.13. For example, the displaying operation 902, moving operations 904 and912, detecting operation 906, and ceasing operation 910, are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 14 shows a functional blockdiagram of an electronic device 1400 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 14 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 14, an electronic device 1400 includes a display unit1402 configured to display a graphic user interface, optionally, a touchsensitive surface unit 1404 configured to receive contacts, and aprocessing unit 1406 coupled to the display unit 1402 and, optionally,the touch-sensitive surface unit 1404. In some embodiments, theprocessing unit 1406 includes a display enabling unit 1408, a detectingunit 1410, and an updating unit 1412.

The processing unit 1406 is configured to enable display (e.g., with thedisplay enabling unit 1408) of a first representation of a current laptime in a user interface, the first representation having a firsttimescale and including a first element, the first element positionedwith respect to the first timescale in accordance with the current laptime on the first timescale; while enabling display of the firstrepresentation, detect (e.g., with the detecting unit 1410) a rotationalmovement of a rotatable input mechanism of the electronic device; and inresponse to the rotational movement: update (e.g., with the updatingunit 1412) the first representation of the current lap time to have asecond timescale, different from the first timescale, in accordance withthe rotational movement and update (e.g., with the updating unit 1412)the position of the first element in accordance with the current laptime on the second timescale.

In some embodiments, updating the first representation to have thesecond timescale comprises selecting the second timescale from aplurality of predefined timescales.

In some embodiments, the rotational movement of the rotatable inputmechanism corresponds to a first input timescale, different from each ofthe plurality of predefined timescales, and selecting the secondtimescale from the plurality of predefined timescales comprises:determining which of the plurality of predefined timescales is closestto the first input timescale and selecting the closest timescale of thepredefined timescales as the second timescale.

In some embodiments, updating the first representation comprisesenabling display of an animation of the first representation changingfrom the first timescale to the second timescale.

In some embodiments, the first representation of the current lap timeincludes a second representation of the current lap time, the secondrepresentation having a third timescale, different from the firsttimescale, the processing unit further configured to: in response to therotational movement, update (e.g., with the updating unit 1412) thesecond representation of the current lap time to have a fourthtimescale, different from the second timescale, in accordance with therotational movement.

The operations described above with reference to FIG. 10 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.14. For example, display operation 1002, detecting operation 1004, andupdating operation 1008 are, optionally, implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 15 shows a functional blockdiagram of an electronic device 1500 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 15 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 15, an electronic device 1500 includes a display unit1502 configured to display a graphic user interface, optionally, a touchsensitive surface unit 1504 configured to receive contacts, and aprocessing unit 1506 coupled to the display unit 1502 and, optionally,the touch-sensitive surface unit 1504. In some embodiments, theprocessing unit 1506 includes a display enabling unit 1508, a detectingunit 1510, and an updating unit 1512.

The processing unit 1506 is configured to enable display (e.g., with thedisplay enabling unit 1508) of a timer representation in a userinterface, the timer representation including: an analog representation,the analog representation including a current duration indicatorrepresenting a current duration setting, and a digital representationrepresenting the current duration setting; while enabling display of thetimer representation, detect (e.g., with the detecting unit 1510) arotational movement of a rotatable input mechanism; and in response tothe rotational movement, update (e.g., with the updating unit 1512) thecurrent duration indicator and the digital representation in accordancewith the rotational movement.

In some embodiments, the digital representation comprises a firstportion and a second portion, the processing unit further configured to,prior to detecting the rotational movement of the rotatable inputmechanism, detect (e.g., with the detecting unit 1510) selection of thefirst portion of the digital representation, where updating the currentduration indicator and the digital representation comprises updating afirst unit of the current duration setting in accordance with therotational movement and the selection of the first portion of thedigital representation and updating the current duration indicator andthe first portion of the digital representation to reflect the updatedfirst unit of the current duration setting.

In some embodiments, the processing unit is further configured to, inresponse to detecting the selection of the first portion of the digitalrepresentation, enable display (e.g., with the display enabling unit1508) of a first visual cue indicating the selection of the firstportion of the digital representation.

In some embodiments, the digital representation comprises a firstportion and a second portion, the processing unit further configured todetect (e.g., with the detecting unit 1510) selection of the secondportion of the digital representation, detect (e.g., with the detectingunit 1510) a second rotational movement of the rotatable inputmechanism, and in response to the second rotational movement: update(e.g., with the updating unit 1512) a second unit of the currentduration setting, different from the first unit, in accordance with thesecond rotational movement and the selection of the second portion ofthe digital representation and update (e.g., with the updating unit1512) the current duration indicator and the second portion of thedigital representation to reflect the updated second unit of the currentduration setting.

In some embodiments, the processing unit is further configured to, inresponse to detecting the selection of the second portion of the digitalrepresentation, enable display (e.g., with the display enabling unit1508) of a second visual cue indicating the selection of the secondportion of the digital representation.

In some embodiments, the processing unit is further configured to, inresponse to detecting the selection of the first portion of the digitalrepresentation, update (e.g., with the updating unit 1512) the analogrepresentation to have a first predefined timescale corresponding to thefirst unit of the current duration setting.

In some embodiments, the processing unit is further configured to, inresponse to detecting the selection of the second portion of the digitalrepresentation, update the analog representation to have a secondpredefined timescale corresponding to the second unit of the currentduration setting.

In some embodiments, the current duration indicator is located on aperimeter of the analog representation, and updating the currentduration indicator comprises updating the location of the currentduration indicator along the perimeter of the analog representation.

In some embodiments, the current duration indicator comprises a dot.

In some embodiments, the current duration indicator comprises a regionextending from a first location along a perimeter of the analogrepresentation to a second location along the perimeter of the analogrepresentation, the first location corresponding to a duration settingof zero, and the second location corresponding to the current durationsetting.

The operations described above with reference to FIG. 11 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.15. For example, display operation 1102, detecting operation 1106, andupdating operation 1108 are, optionally, implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying figures, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe appended claims.

What is claimed is:
 1. A non-transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by one or more processors of anelectronic device with a display, cause the device to: display, at afirst time, a first representation of a first lap time in a userinterface; display an animation of movement of the first representationalong a first axis in the user interface that progresses as time elapsesfrom the first time, wherein the animation of movement of the firstrepresentation is contained within a first region of the user interface;while moving the first representation within the first region of theuser interface, detect a first lap input at the device at a second time;and in response to detecting the first lap input: cease to display theanimation of movement of the first representation along the first axis;move the first representation to a second region of the user interfacedifferent from the first region; and while concurrently displaying thefirst representation within the second region of the user interface:display a second representation of a second lap time in the userinterface; and display an animation of movement of the secondrepresentation along the first axis in the user interface thatprogresses as time elapses from the second time, wherein the animationof movement of the second representation is contained within the firstregion of the user interface, wherein a relative positioning of thefirst representation and the second representation along the first axiscorresponds to a difference between the first lap time and the secondlap time.
 2. The non-transitory computer readable storage medium ofclaim 1, wherein the first and second representations are separated by adistance in a direction orthogonal to the first axis in the userinterface.
 3. The non-transitory computer readable storage medium ofclaim 1, wherein the first and second representations are connected by aline in the user interface.
 4. The non-transitory computer readablestorage medium of claim 1, wherein the first and second representationscomprise a first stopwatch view, the non-transitory computer readablestorage medium further comprising instructions which when executed bythe one or more processors of the electronic device, cause the deviceto: detect a view change input at the device; and in response to theview change input, display a second stopwatch view, different from thefirst stopwatch view, the second stopwatch view including informationabout the first lap time and the second lap time.
 5. The non-transitorycomputer readable storage medium of claim 1, further comprisinginstructions which when executed by the one or more processors of theelectronic device, cause the device to: detect a lap time display inputon a touch-sensitive surface of the device, the lap time display inputcomprising a contact and movement of the contact on the touch-sensitivesurface; and in response to the lap time display input, display a listof lap times including the first lap time and the second lap time. 6.The non-transitory computer readable storage medium of claim 5, furthercomprising instructions which when executed by the one or moreprocessors of the electronic device, cause the device to: in response tothe lap time display input, modify the display of the first and secondrepresentations so as to reduce a display area of the first and secondrepresentations in the user interface.
 7. The non-transitory computerreadable storage medium of claim 1, wherein: a first dimension of theuser interface along the first axis is displayed at a first timescale,the first timescale having a first maximum lap time, and the second laptime exceeds the first maximum lap time, the non-transitory computerreadable storage medium further comprising instructions which whenexecuted by the one or more processors of the electronic device, causethe device to: while the second lap time exceeds the first maximum laptime, detect a second lap input at the device at a third time; and inresponse to the second lap input: determine a second timescale having asecond maximum lap time greater than the second lap time; and update thefirst dimension of the user interface to have the second timescale. 8.The non-transitory computer readable storage medium of claim 1, whereinthe first representation and the second representation providerespective visual cues of their respective lap times.
 9. Thenon-transitory computer readable storage medium of claim 1, furthercomprising instructions which when executed by the one or moreprocessors of the electronic device, cause the device to: display astopwatch representation in addition to the first representation and thesecond representation, the stopwatch representation includinginformation about the second lap time.
 10. The non-transitory computerreadable storage medium of claim 1, further comprising instructionswhich when executed by the one or more processors of the electronicdevice, cause the device to: detect a second lap input at the device ata third time, the third time being after the second time; in response tothe second lap input, determine an average lap time based on the firstlap time and the second lap time; and display a representation of theaverage lap time in the user interface.
 11. The non-transitory computerreadable storage medium of claim 10, wherein the representation of theaverage lap time in the user interface includes a visual line that isorthogonal to the first axis.
 12. The non-transitory computer readablestorage medium of claim 1, further comprising instructions which whenexecuted by the one or more processors of the electronic device, causethe device to: prior to displaying the animation of movement of thefirst representation along the first axis in the user interface, measurea first amount of time elapsed since the first time, wherein moving thefirst representation along the first axis is in accordance with themeasured first amount of time; and prior to displaying the animation ofmovement of the second representation along the first axis in the userinterface, measure a second amount of time elapsed since the secondtime, wherein moving the second representation along the first axis isin accordance with the measured second amount of time.
 13. Thenon-transitory computer readable storage medium of claim 1, wherein: thefirst representation is displayed at a first location in the userinterface after the animation of movement of the first representationceases to be displayed, and the second representation is initiallydisplayed at a second location in the user interface that is differentfrom the first location.
 14. The non-transitory computer readablestorage medium of claim 1, wherein: the first representation moves alongthe first axis in the user interface in a first direction, and thesecond representation moves along the first axis in the user interfacein the first direction.
 15. The non-transitory computer readable storagemedium of claim 1, wherein the one or more programs further compriseinstructions, which when executed by the one or more processors, causethe device to: display, at the first time and during display of theanimation of movement of the first representation, a first lap numberrepresentation along the first axis, the first lap number representationcorresponding to the first representation; in response to detecting thefirst lap input: move the first lap number representation to a locationalong a second axis different from the first axis; and display a secondlap number representation along the first axis, the second lap numberrepresentation corresponding to the second representation.
 16. A method,comprising: at a device with one or more processors and memory:displaying, at a first time, a first representation of a first lap timein a user interface; displaying an animation of movement of the firstrepresentation along a first axis in the user interface that progressesas time elapses from the first time, wherein the animation of movementof the first representation is contained within a first region of theuser interface; while moving the first representation within the firstregion of the user interface, detecting a first lap input at the deviceat a second time; and in response to detecting the first lap input:ceasing to display the animation of movement of the first representationalong the first axis; move the first representation to a second regionof the user interface different from the first region; and whileconcurrently displaying the first representation within the secondregion of the user interface: displaying a second representation of asecond lap time in the user interface; and displaying an animation ofmovement of the second representation along the first axis in the userinterface that progresses as time elapses from the second time, whereinthe animation of movement of the second representation is containedwithin the first region of the user interface, wherein a relativepositioning of the first representation and the second representationalong the first axis corresponds to a difference between the first laptime and the second lap time.
 17. The method of claim 16, wherein thefirst and second representations are separated by a distance in adirection orthogonal to the first axis in the user interface.
 18. Themethod of claim 16, wherein the first and second representations areconnected by a line in the user interface.
 19. The method of claim 16,wherein the first and second representations comprise a first stopwatchview, the method further comprising: detecting a view change input atthe device; and in response to the view change input, displaying asecond stopwatch view, different from the first stopwatch view, thesecond stopwatch view including information about the first lap time andthe second lap time.
 20. The method of claim 16, further comprising:detecting a lap time display input on a touch-sensitive surface of thedevice, the lap time display input comprising a contact and movement ofthe contact on the touch-sensitive surface; and in response to the laptime display input, displaying a list of lap times including the firstlap time and the second lap time.
 21. The method of claim 20, furthercomprising: in response to the lap time display input, modifying thedisplay of the first and second representations so as to reduce adisplay area of the first and second representations in the userinterface.
 22. The method of claim 16, wherein: a first dimension of theuser interface along the first axis is displayed at a first timescale,the first timescale having a first maximum lap time, and the second laptime exceeds the first maximum lap time, the method further comprising:while the second lap time exceeds the first maximum lap time, detectinga second lap input at the device at a third time; and in response to thesecond lap input: determining a second timescale having a second maximumlap time greater than the second lap time; and updating the firstdimension of the user interface to have the second timescale.
 23. Themethod of claim 16, wherein the first representation and the secondrepresentation provide respective visual cues of their respective laptimes.
 24. The method of claim 16, further comprising: displaying astopwatch representation in addition to the first representation and thesecond representation, the stopwatch representation includinginformation about the second lap time.
 25. The method of claim 16,further comprising: detecting a second lap input at the device at athird time, the third time being after the second time; in response tothe second lap input, determining an average lap time based on the firstlap time and the second lap time; and displaying a representation of theaverage lap time in the user interface.
 26. The method of claim 25,wherein the representation of the average lap time in the user interfaceincludes a visual line that is orthogonal to the first axis.
 27. Themethod of claim 16, further comprising: prior to displaying theanimation of movement of the first representation along the first axisin the user interface, measuring a first amount of time elapsed sincethe first time, wherein moving the first representation along the firstaxis is in accordance with the measured first amount of time; and priorto displaying the animation of movement of the second representationalong the first axis in the user interface, measuring a second amount oftime elapsed since the second time, wherein moving the secondrepresentation along the first axis is in accordance with the measuredsecond amount of time.
 28. The method of claim 16, wherein: the firstrepresentation is displayed at a first location in the user interfaceafter the animation of movement of the first representation ceases to bedisplayed, and the second representation is initially displayed at asecond location in the user interface that is different from the firstlocation.
 29. The method of claim 16, wherein: the first representationmoves along the first axis in the user interface in a first direction;and the second representation moves along the first axis in the userinterface in the first direction.
 30. The method of claim 16, furthercomprising: displaying, at the first time and during display of theanimation of movement of the first representation, a first lap numberrepresentation along the first axis, the first lap number representationcorresponding to the first representation; in response to detecting thefirst lap input: moving the first lap number representation to alocation along a second axis different from the first axis; anddisplaying a second lap number representation along the first axis, thesecond lap number representation corresponding to the secondrepresentation.
 31. An electronic device, comprising: a display; one ormore processors; a memory; and one or more programs, where in the one ormore programs are stored in the memory and configured to be executed bythe one or more processors, the one or more programs includinginstructions for: displaying, at a first time, a first representation ofa first lap time in a user interface; displaying an animation ofmovement of the first representation along a first axis in the userinterface that progresses as time elapses from the first time, whereinthe animation of movement of the first representation is containedwithin a first region of the user interface; while moving the firstrepresentation within the first region of the user interface, detectinga first lap input at the device at a second time; and in response todetecting the first lap input: ceasing to display the animation ofmovement of the first representation along the first axis; move thefirst representation to a second region of the user interface differentfrom the first region; and while concurrently displaying the firstrepresentation within the second region of the user interface:displaying a second representation of a second lap time in the userinterface; and displaying an animation of movement of the secondrepresentation along the first axis in the user interface thatprogresses as time elapses from the second time, wherein the animationof movement of the second representation is contained within the firstregion of the user interface, wherein a relative positioning of thefirst representation and the second representation along the first axiscorresponds to a difference between the first lap time and the secondlap time.
 32. The electronic device of claim 31, wherein the first andsecond representations are separated by a distance in a directionorthogonal to the first axis in the user interface.
 33. The electronicdevice of claim 31, wherein the first and second representations areconnected by a line in the user interface.
 34. The electronic device ofclaim 31, wherein the first and second representations comprise a firststopwatch view, the one or more programs further including instructionsfor: detecting a view change input at the device; and in response to theview change input, displaying a second stopwatch view, different fromthe first stopwatch view, the second stopwatch view includinginformation about the first lap time and the second lap time.
 35. Theelectronic device of claim 31, the one or more programs furtherincluding instructions for: detecting a lap time display input on atouch-sensitive surface of the device, the lap time display inputcomprising a contact and movement of the contact on the touch-sensitivesurface; and in response to the lap time display input, displaying alist of lap times including the first lap time and the second lap time.36. The electronic device of claim 35, further comprising: in responseto the lap time display input, modifying the display of the first andsecond representations so as to reduce a display area of the first andsecond representations in the user interface.
 37. The electronic deviceof claim 31, wherein: a first dimension of the user interface along thefirst axis is displayed at a first timescale, the first timescale havinga first maximum lap time, and the second lap time exceeds the firstmaximum lap time, the one or more programs further includinginstructions for: while the second lap time exceeds the first maximumlap time, detecting a second lap input at the device at a third time;and in response to the second lap input: determining a second timescalehaving a second maximum lap time greater than the second lap time; andupdating the first dimension of the user interface to have the secondtimescale.
 38. The electronic device of claim 31, wherein the firstrepresentation and the second representation provide respective visualcues of their respective lap times.
 39. The electronic device of claim31, the one or more programs further including instructions for:displaying a stopwatch representation in addition to the firstrepresentation and the second representation, the stopwatchrepresentation including information about the second lap time.
 40. Theelectronic device of claim 31, the one or more programs furtherincluding instructions for: detecting a second lap input at the deviceat a third time, the third time being after the second time; in responseto the second lap input, determining an average lap time based on thefirst lap time and the second lap time; and displaying a representationof the average lap time in the user interface.
 41. The electronic deviceof claim 40, wherein the representation of the average lap time in theuser interface includes a visual line that is orthogonal to the firstaxis.
 42. The electronic device of claim 31, the one or more programsfurther including instructions for: prior to displaying an animation ofmovement of the first representation along the first axis in the userinterface, measuring a first amount of time elapsed since the firsttime, wherein moving the first representation along the first axis is inaccordance with the measured first amount of time; and prior todisplaying an animation of movement of the second representation alongthe first axis in the user interface, measuring a second amount of timeelapsed since the second time, wherein moving the second representationalong the first axis is in accordance with the measured second amount oftime.
 43. The electronic device of claim 31, wherein: the firstrepresentation is displayed at a first location in the user interfaceafter the animation of movement of the first representation ceases to bedisplayed, and the second representation is initially displayed at asecond location in the user interface that is different from the firstlocation.
 44. The electronic device of claim 31, wherein: the firstrepresentation moves along the first axis in the user interface in afirst direction; and the second representation moves along the firstaxis in the user interface in the first direction.
 45. The electronicdevice of claim 31, the one or more programs further includinginstructions for: displaying, at the first time and during display ofthe animation of movement of the first representation, a first lapnumber representation along the first axis, the first lap numberrepresentation corresponding to the first representation; in response todetecting the first lap input: moving the first lap numberrepresentation to a location along a second axis different from thefirst axis; and displaying a second lap number representation along thefirst axis, the second lap number representation corresponding to thesecond representation.